Known Issues
This page lists important information about issues that apply to PlanetPress Connect 2018.1.
Business Graphics: Backward Compatibility Issues
As a consequence of changes in both the user interface and the underlying technology, Business Graphics made with a version prior to PlanetPress Connect 2018.1 may not display correctly when opened in version 2018.1.
The currently known backward compatibility issues are listed here:
All charts
- Legend position: The position of the legend is not converted. It defaults to 'left' in a converted chart.
- Rows are series/Columns are series: Only one type of data structure for detail tables is supported in the new version: the one that corresponds to the former Columns are series setting (with which charts display one series per record, one bar/point per data field). After conversion to 2018.1, charts that used the Rows are series setting will be displayed as if the Columns are series setting were used. Pie charts will thus only show data from the first record in the detail table. If the number of records in the detail table remains consistent, then the charts can be corrected by modifying the data mapping configuration (see Preparing a data table). Otherwise the data needs to be transposed via script.
- NOTE: Expanded custom chart scripts cannot be converted.
Pie charts
- Default colors: The default colors (used when no pie chart colors are specified) have changed.
Line and Bar charts
- Legend label: In previous versions, the name for a values series (needed for the legend) could only be taken from a field outside the detail table. The value of the selected field would be used. Setting a different label required expanding the chart script. After conversion, the name of the field is used instead of the value. Setting a different label can now be done in the Edit Chart Script dialog (see Selecting data in a Business Graphic script).
Minor differences in PCL output introduced in 2018.1
The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox.
However this update could lead to increased output file sizes for some PCL jobs. This is generally not a cause for concern, however there might be some associated increase in processing times, as well as some minor differences in the output. For example, table line widths and font spacings might differ slightly (particularly for SMALL CAPS text), which could lead to slightly different word-wrapping in some circumstances.
Windows Server 2016 issue
As of PlanetPress Connect 2018.1 Connect is officially supported under Windows Server 2016.
Please note, however, that the Objectif Lune Inc. Update Client application might be blocked by the enhanced security settings in Windows Server 2016.
To fix this, add http://updates.ca.objectiflune.com to the list of trusted web sites on that machine, or lower the internet access rules.
No switch for case sensitivity in Dynamic Printer Rules editor
Case sensitivity/insensitivity has not been introduced as an option in the first cut (PlanetPress Connect2018.1) of the Dynamic Printer rules editor. This option will be added in a subsequent version.
Limit of 100MB of image files within a single job
The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox.
However this update also introduced a limit of 100MBs for image files included within a single job. The limit is set at 100MB deliberately, as this allows most jobs to run faster. However, if a job requires more than 100MBs of image files, then the Connect image cache size can be increased to cater for such.
Please contact OL Support for instructions on how to modify the image memory cache value, if needed.
Print Output: Booklet Impositioning changes introduced in 2018.1
When Booklet Impositioning is enabled, all pages within a document need to be changed to duplex prior to Impositioning . The method for duplexing jobs has been changed to now always combine existing pages into the front and backsides of sheets, rather than adding empty backsides to any simplex pages.
The result is that now every document in the job becomes a booklet without any empty pages between the first page and the last page.
With some exceptions. Booklet Impositioning that require a multiple of 4 pages (Saddle binding and Perfect binding) will still get empty pages added, when needed.
Change in boundaries.find() function in 2018.1
In PlanetPress Connect 1.8 and previous versions, the DataMapper's boundaries.find() function returned the region searched within PDF files, whereas for text files it returned the exact region where the text was found. In 2018.1 this was changed so that boundaries.find() on PDFs would return the exact region where the text was found, the same as for text files. However, it was subsequently found that this could cause issues with previously created templates using the function on PDF files. Consequently, this change was reverted in 2018.1.1.
Customers experiencing issues as a result of the changed functionality in version 2018.1 will need to update to Connect 2018.1.1.
Issues with Microsoft Edge browser
The Microsoft Edge browser fails to display web pages when the Workflow's CORS option (in the HTTP Server Input 2 section) is set to "*". This issue will be resolved in a future release.
Installation Paths with Multi-Byte Characters
When installing the
Switching Languages
Changing the language using the Window>Preferences>Language Setting menu option does not currently change all of the strings in the application to the selected language. This is a known issue and will be fixed in a later release.In the meantime we offer the following workaround for anyone who needs to change the language:
- Go to the .ini files for the Designer and Server Config:
C:\Program Files\Objectif Lune\OL Connect\Connect Designer\Designer.iniC:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.ini
- Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | ko | pt | tw | zh
Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.
GoDaddy Certificates
When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next. In some cases, however, this may not work correctly. For this reason those users should activate Place all certificates in the following store and then select the Trusted Root Certification Authorities as the target certificate store.
MySQL Compatibility
After installing Connect 2018.1 a downgrade to a Connect version earlier than Connect 1.3 or to a MySQL version earlier than 5.6.25 is not seamlessly possible. This is because the database model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions. If you need to switch to an older version of Connect / MySQL, it is first necessary to remove the Connect MySQL Database folder from "%ProgramData%\Connect\MySQL\data" before installing the older version.
The minimum supported MySQL version is 5.1.31.
PostScript Print Presets
The print presets for PostScript were changed from Version 1.1 onwards meaning that some presets created in Version 1.0 or 1.0.1 may no longer work.Any PostScript print preset from Version 1.0 that contains the following will not work in Version 2018.1: *.all[0].*
Any preset containing this code will need to be recreated in Version 2018.1.
Available Printer Models
Note that only the single Printer Model (Generic PDF) will appear on the Advanced page of the Print Wizard by default.To add additional printer models click on the settings 
button next to the Model selection entry box.
Note that the descriptions of some of the printers were updated in version 1.2 meaning that if you had version 1.n installed, you may find that the same printer style appears twice in the list, but with slightly different descriptions.
For example the following printer types are actually identical:
- Generic PS LEVEL2 (DSC compliant)
- Generic PS LEVEL2 (DSC)
External Resources in Connect
There are certain limitations on how external resources can be used in Connect. For example if you want to link a file (e.g., CSS, image, JavaScript etc.) from a location on the network but you do not want to have a copy of the file saved with the template you need to do the following:- The resource must be located where it can be accessed by all Servers/Slaves run as users. Failure to do this will cause the image to appear as a Red X in the output for all documents which were merged by engines which could not access the file. The job will terminate normally and the error will be logged.
- The file must be referenced via a UNC path e.g.,
file://///w2k8r2envan/z%20images/Picture/Supported/JPG/AB004763.jpg
- UNC paths are required because the services will be unable to access mapped network drives (Windows security feature).
- The engine processing the job will look on the local file system for the direct file path leading to the “resource not found” issue mentioned above.
Important Note: The Designer itself and Proof Print do not use processes that run as services and they may find local files with non-UNC paths which can lead to the false impression that the resources are correct.
Using Capture After Installing Workflow 8
If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, Capture can no longer be used within Workflow 7. The plugins are now registered uniquely to Workflow 8 and the Messenger for Workflow 7 is taken offline. It is only possible to use Capture from PlanetPress Connect Workflow 8 thereafter.
Capturing Spool Files After Installing Workflow 8
If PlanetPress Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, the PlanetPress Suite 7 option to capture spool files from printer queues will no longer function. The solution is to use PlanetPress Connect Workflow 8 to capture spool files from printer queues.
Colour Model in Stylesheets
The colour model of colours defined in a stylesheet can sometimes change after editing the stylesheet. This is a known issue and will be addressed in a subsequent release.
Image Preview in Designer
If in the Windows Internet settings (Connection Settings > LAN configuration) a proxy is enabled, but "Bypass proxy settings for local addresses" is not checked, the image preview service, conversion service and live preview tab in the Designer will not work and exhibit the following issues:- Images will be shown as 0 size boxes (no red 'X' is displayed)
- Live preview does not progress, and when re-activated reports "browsers is busy"
To fix the issue you must check the "Bypass proxy settings for local addresses" option
Merge\Weaver Engines when Printing
The print operation in the Designer will automatically detect whether the Merge\Weaver engines are available and display a message for the user to retry or cancel if not. Once the Merge\Weaver engine becomes available and the user presses retry the print operation will proceed as normal. This message can also occur in the following circumstances:- If the server is offline and you are not using Proof Print
- On some occasions before the Print Wizard opens
REST Calls for Remote Services
The Server will now accept REST calls for all remote services and will make commands wait indefinitely until the required engines become available. The Server will log when it is waiting for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server.
Print Content and Email Content in PlanetPress Workflow
In PlanetPress Workflow’s Print Content and Email Content tasks, the option to Update Records from Metadata will only work for fields whose data type is set to String in the data model. Fields of other types will not be updated in the database and no error will be raised. This will be fixed in a later release.
Print Limitations when the Output Server is located on a different machine
The following limitation may occur when using the Print options from a Designer located on a different machine to the Output Server:- The file path for the prompt and directory output modes is evaluated on both the client AND server side. When printing to a network share it must be available to BOTH the Designer and Server for the job to terminate successfully.
- The Windows printer must be installed on both the Server and Designer machines.
- When printing via the Server from a remote Designer, the output file remains on the Server machine. This is remedied by selecting “Output Local” in the Output Creation configuration